* Contribute

/For security issues, please read the ~Security.org~ file./

Any contribution that helps improving the code's security, performance,
documentation, tests and CI is welcome.

New features are almost always consider anti-features. Consider writing
an expansion (or plugin) instead.

** Setup

Developer's build environment, and notes describing important files,
and directories.

** Report Priority

As a solo maintainer, reports get prioritize according to

- Severity
- Number of users affected

** Issue Guidelines

Post a complete description of the issue using this template

#+BEGIN_SRC markdown
# Issue Title

## I did this
[self-contained example]

## I expected
[previous behavior]

## Instead got
[backtrace or behavior description]

## Project version
[project -V]

## Dependency versions
[OS, and other relevant dependencies]
#+END_SRC

Please make a documentation related pull request based on your question,
it's answer, and related discussion when appropriate.

** Patch Guidelines

/Patches can be delivered as pull requests, or emails./

- All patches are contributed under ~License.org~. Do not submit a patch
  if that isn't the case.
- Include tests for substantial bug fixes.
- Alternatively, provide just the tests describing the expected behavior.
- Follow the style conventions of the surrounding code.
- Strip trailing white space.
- Update documentation.

** Code of Conduct

This code of conduct applies to all of the project's current, and future,
collaborative spaces, such as the hosted source code, it's issue
tracker, and official mirrors.

- Discussion should be limited to the project, and related technologies.
- Participants must ensure their language, and actions, are free of
  personal attacks and remarks disparaging to anyone.
- Behaviour which can be reasonably considered harassment will not be
  tolerated, and may result in being expelled from these spaces.

You may report any violation to the project maintainer at
~maintainer@example.com~.
